Selectively enabling multi-factor authentication for managed devices

ABSTRACT

Disclosed are various examples of selectively enabling multi-factor authentication for applications on managed devices. An identity provider receives an authentication request for a first client application executed in a managed client device. The authentication request includes a first authentication factor corresponding to a management credential. The identity provider then determines whether one or more second authentication factors should be requested. If so, the identity provider then requests the second authentication factor(s) from a second client application. The identity provider receives the second authentication factor(s) from the second client application. The identity provider then authenticates the first client application in response to verifying the first authentication factor and the second authentication factor(s).

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to U.S. patent application entitled “MULTI-FACTOR AUTHENTICATION FOR MANAGED APPLICATIONS USING SINGLE SIGN-ON TECHNOLOGY” and filed on even date herewith under Attorney Docket Number W237.01, which is incorporated herein by reference in its entirety.

BACKGROUND

Multi-factor authentication systems are becoming increasingly popular for computing system account security. Traditionally, users have provided a username and a password to log into a user account. However, malicious users can also gain access to the user account simply by having knowledge of the username and the password. In other words, username and password systems rely only on two items of information that the user knows. Thus, such systems rely exclusively on knowledge-based authentication factors.

Other authentication factors can include what the user has (possession factors) and who the user is (inherence factors). Examples of possession factors can include possession of a trusted device (e.g., smartwatch, smartphone, or other device with a long-lived credential stored thereon or able to communicate by way of a trusted telephone number or email address), possession of a key-fob token that generates one-time passwords, and possession of a smartcard. Examples of inherence factors can include retinal scans, iris scans, and fingerprint scans. Adding possession and/or inherence factors to an authentication system that uses username and password-based authentication can greatly improve security. Also, requiring answers to other knowledge-based questions can improve security. The questions can be dynamically generated based on transaction histories (e.g., “which of following is the correct purchase amount of your transaction yesterday?”), or credit histories, or may be based on static answers to questions that are preconfigured by the user (e.g., “who was your favorite school teacher?”).

Unfortunately, it can be difficult to practically implement multi-factor authentication in native applications. Application developers would have to write custom authentication code and/or include code from a software development kit that enables multi-factor authentication, but it can be very challenging to convince developers to do this. As a consequence, an organization that manages devices, such as under a bring-your-own-device model, cannot require multi-factor authentication for native applications under existing approaches.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the present disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, with emphasis instead being placed upon clearly illustrating the principles of the disclosure. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.

FIG. 1 is a drawing of a networked environment according to various examples of the disclosure.

FIG. 2 is a sequence diagram illustrating an example component interaction according to various examples of the present disclosure.

FIGS. 3-8 are flowcharts illustrating examples of functionality according to various examples of the present disclosure.

DETAILED DESCRIPTION

The present disclosure relates to enabling multi-factor authentication for applications on managed devices. Convincing developers of applications to include code that supports multi-factor authentication is for many reasons impractical. However, as will be described, single sign-on systems that are already supported on managed devices can be extended to support multi-factor authentication. Managed applications can support a single sign-on experience through the use of an identity provider. With a single sign-on experience, a user enters a single set of security credentials for an account and, upon authentication, the user is able to access multiple different applications and services that are linked to that account. In some operating systems, such as IOS, the operating system itself can include support for single sign-on. As will be described, the identity provider that supports existing single sign-on approaches for managed devices can be modified to include a multi-factor authentication adapter. This adapter, when enabled, can require the user to provide one or more authentication factors using the same device or another trusted device before permitting authentication.

Furthermore, in various embodiments, administrators of an organization that manages devices can selectively enable multi-factor authentication for specific applications. This configuration can be static or dynamic. If dynamic, whether multi-factor authentication is enabled for a given application can change based upon a variety of factors such as device status, device location, network status, and other factors.

With reference to FIG. 1, shown is a networked environment 100 according to various examples. The networked environment 100 can include a plurality of client devices 103 a and 103 b, a device management service 104, an identity provider 106, and a plurality of service providers 109 a . . . 109N, which can be in data communication with one another over the network 112. The network 112 includes, for example, the Internet, one or more intranets, extranets, wide area networks (WANs), local area networks (LANs), wired networks, wireless networks, other suitable networks, or any combination of two or more such networks. For example, the networks can include satellite networks, cable networks, Ethernet networks, and other types of networks.

The device management service 104, the identity provider 106, and the service providers 109 can include, for example, a server computer or any other system providing computing capabilities. Alternatively, the device management service 104, the identity provider 106, and the service providers 109 can employ multiple computing devices that can be arranged, for example, in one or more server banks, computer banks, or other arrangements. The computing devices can be located in a single installation or can be distributed among many different geographical locations. For example, the device management service 104, the identity provider 106, and the service providers 109 can include multiple computing devices that together form a hosted computing resource, a grid computing resource, or any other distributed computing arrangement. In some cases, the device management service 104, the identity provider 106, and the service providers 109 can operate as at least a portion of an elastic computing resource where the allotted capacity of processing, network, storage, or other computing-related resources can vary over time. The device management service 104, the identity provider 106 and the service providers 109 can also include or be operated as one or more virtualized computer instances. Generally, the device management service 104, the identity provider 106 and the service providers 109 can be operated in accordance with particular security protocols such that they are considered trusted computing environments.

The device management service 104 can manage or oversee the operation of multiple client devices 103. In some examples, an enterprise, such as one or more companies or other organizations, can operate the device management service 104 to oversee or manage the operation of the client devices 103 of employees, contractors, or other users within an enterprise environment. In this sense, the client devices 103 can include managed devices that are managed by the device management service 104.

To facilitate management of client devices 103, the device management service 104 can establish a secure communications channel with the client devices 103 (e.g., a mobile device management channel, or MDM channel). The device management service 104 can establish the secure communications channel by creating a secure communication link with the client device 103. A secure communication link can be established using MDM application programming interfaces (APIs) that are provided by an operating system executed by the client device 103. In some examples, the secure communications channel can be established using a push notifications framework or notification service provided by an operating system ecosystem associated with the client device 103 that allows for communications between the device management service 104 and a client device 103 over the network 112 that are encrypted using a digital certificate.

The client device 103 a can be enrolled as a managed device with the device management service 104 through APIs provided by the operating system. The enrollment process can include authentication of a user's credentials. Upon authentication of a user's credentials by the device management service 104, the client device 103 a, using the MDM APIs of the operating system, can enroll the client device 103 a as a managed device so that various management functions can be securely performed over the secure communications channel.

Examples of management functions can include commands to erase certain data from the client device 103 a, commands to install certain applications or application updates, commands to lock a client device 103 a or activate a display lock feature, a command to remotely perform a factory reset of the client device 103 a, or other management functions. Additionally, data can be securely transmitted through the secure communications channel to the client device 103 a or applications executed by the client device 103 a.

Additionally, the operating system of the client device 103 a can also provide the ability to create access-restricted storage that is associated with particular applications installed on the client device 103 a. Access-restricted storage can be associated with multiple applications that are installed on the client device 103 a through the secure communications channel. In some scenarios, applications that are signed by a common certificate can be provided access to the access-restricted storage of each other, whereas applications that are not signed by the certificate do not have access to the access-restricted storage of other applications. Additionally, the device management service 104 can transmit data to the client device 103 a over the secure communications channel that can be stored in the access-restricted storage such that it is accessible by certain applications and inaccessible to other applications that are installed on the client device 103 a.

The secure communications channel can be encrypted or secured using a digital certificate that is associated with the client device 103 a, the device management service 104, or an enterprise with which the client device 103 a is associated. In one scenario, the device management service 104 can obtain a security certificate, such as a secure sockets layer (SSL) certificate, that is unique to a particular enterprise with which a client device 103 a is associated. In one example, an administrator associated with the enterprise can provide a certificate to the device management service 104 using an administrator console or other functionality with which a certificate can be uploaded. The certificate can also be signed by a certificate authority, which can in some cases be operated by the device management service 104. The device management service 104 can encrypt or secure the secure communications channel using the certificate so that the secure communications channel is a secure communication link over the network 112 through which data can be sent to the client device 103.

Additionally, the device management service 104 can specify that data sent through the secure communications channel can only be accessed by certain applications installed on the client device 103 a. The applications that can access data sent through the secure communications channel can also be restricted in how certain data can be manipulated, viewed or handled on the client device 103 a. For example, an application installed on the client device 103 a can be coded to restrict the ability of a user to capture, share, or otherwise remove data from the client device 103 a that is received through the secure communications channel.

The device management service 104 can also facilitate ensuring that client devices 103 aa that are administered by the device management service 104 are operating in compliance with various compliance rules. In one scenario, the device management service 104 can issue management commands that instruct a client device 103 to take a particular action with respect to a compliance rule. For example, if a client device 103 a is designated as lost or stolen, the device management service 104 can issue a command instructing the client device 103 a to erase data and applications that were previously sent to the client device 103 a through the secure communications channel or other communication links and otherwise stored on the client device 103 a. The device management service 104 can also obtain data from a third party computing environment, such as an application, a security code, authentication token, or other data. As another example, if the device management service 104 determines that a client device 103 a has violated a compliance rule with respect to having unauthorized modifications or unauthorized applications installed on the client device 103 a, the device management service 104 can issue a command instructing the client device 103 a to erase data and applications stored on the client device 103 a. As a further example, the device management service 104 can also issue a command instructing the client device 103 a to activate a display lock of the client device 103 a that requires a user to enter a personal identification number (PIN) in order to use the client device 103 a.

The data stored in the management data store 113 and available to the device management service 104 includes, for example, authentication data, compliance rules, device data, and potentially other data. The authentication data can include data used to verify one or more security credentials presented by a user for authentication. To this end, secure certificates can be stored and then be made available to the client device 103 a that has been authenticated in order to encrypt the secure communications channel and/or for other functions.

Within the context of an enterprise, compliance rules include one or more rules that, when violated, can cause the device management service 104 to issue a management command. Compliance rules can include a list of unauthorized hardware functions, software functions, or applications that potentially pose a threat to enterprise data or to the use of enterprise applications. As noted above, if client device 103 a falls out of compliance with one or more compliance rules, a management command can be transmitted to the client device 103 a instructing the client device 103 a to perform one or more actions specified by the compliance rule. Alternatively, a compliance rule can also reside on the client device 103 a, which can self-enforce compliance rules. The management data store 113 can also include user account data. User account data can include information with which a user account can be authenticated, such as user credentials. User account data can also include data such as email, contact, calendar data, documents, files or other data that is associated with a user account.

Device data can represent data stored in the management data store 113 that is associated with client devices 103 a that are enrolled with the device management service 104 as managed devices. Device data can include a unique device identifier associated with the client device 103 a, device policies that are associated with a particular client device 103 a, status information associated with a particular client device 103 a, and other data that facilitates management of the client device 103 a by the device management service 104. Device data can also include user data that is synchronized with a particular client device 103 a. A user account can be associated with multiple client devices 103. Different client devices 103 associated with a user account can have different user account data stored thereon. For example, a user's smartphone can have a certain number of documents or email messages stored on the device, whereas the user's laptop or tablet can have varying amounts of types of user account data stored on the device.

The identity provider 106 can provide a federated identity service on behalf of the service providers 109. To this end, the identity provider 106 can be in communication with an identity data store 115 that stores information associated with user identities. This information can include, for example, usernames, security credentials, biometric identity information, authorized client applications, unauthorized client applications, authorized client devices 103, unauthorized client devices 103, and so on. As will be described, users are able to authenticate by way of the identity provider 106 in order to access services provided by the multiple service providers 109. The identity provider 106 can include a plurality of platform adapters to facilitate platform-specific authentication on different client platforms, such as IOS, ANDROID, WINDOWS, and so on.

In various embodiments, the identity provider 106 can include a multi-factor authentication (MFA) adapter 116 that enables multi-factor authentication for client devices 103 and service providers 109. Multiple MFA adapters 116 that are platform specific can be provided in some cases. The MFA adapter 116 can function alongside non-multi-factor authentication by the identity provider 106. In particular, the operation of the MFA adapter 116 can be controlled by a set of MFA rules 117 that can enable or disable the MFA adapter 116 in various scenarios.

The service providers 109 provide corresponding services for client applications. The services can include, for example, social networking services, email services, voice communication services, enterprise information management services, productivity services, game services, and so on. In some examples, one or more of the service providers 109 can authenticate users separately from the identity provider 106, thereby giving users the option to log in either with the identity provider 106 or with the service provider 109 directly. It is noted that the service providers 109 need not be aware of the MFA adapter 116. As long as the service providers 109 are configured to use the identity provider 106 for authentication, the identity provider 106 can enable or disable multi-factor authentication using the MFA adapter 116 without involvement of the service providers 109.

The service providers 109 and the identity provider 106 can communicate with the client device 103 over the network 112 by way of hypertext transfer protocol (HTTP), simple object access protocol (SOAP), representational state transfer (REST), and/or other protocols.

Each client device 103 can represent a processor-based system, such as a computer system, that can be embodied in the form of a desktop computer, a laptop computer, a personal digital assistant, a cellular telephone, a smartphone, a set-top box, a music player, a web pad, a tablet computer system, a game console, an electronic book reader, or any other device with like capability. The client devices 103 can include a display 118 that includes, for example, one or more devices such as liquid crystal display (LCD) displays or other types of display devices. The client devices 103 can also be equipped with networking capability or networking interfaces, including a localized networking or communication capability such as an NFC capability, RFID read and/or write capability, a microphone and/or speaker, or other localized communication capability.

The client device 103 a can execute various applications, such as a management application 121, a plurality of client applications 124 a . . . 124N, and other applications, services, or processes. The management application 121 can receive security credentials from a user and to authenticate with the device management service 104. Upon authentication with the device management service 104, the management application 121 is able to obtain single sign-on (SSO) credentials 125, which in turn allow the client applications 124 to request identity assertions from the identity provider 106 in order to authenticate the client applications 124 with the respective service providers 109 as will be described. Although described as an application, it is understood that the management application 121 can be an integral component of an operating system of the client device 103. Also, in some scenarios, the SSO credentials 125 can be provisioned directly to the operating system for all client applications 124 to use. This can be performed under IOS using either a certificate profile that is installed in a managed certificate keychain or a combination of a certificate and a Kerberos profile together. Rather than being stored in the management application 121, the SSO credentials 125 can be stored in the operating system itself in these scenarios. Access rules 126 can restrict which client applications 124 are permitted to use the SSO credentials 125 for authenticating with identity providers 106. In various implementations, the access rules 126 can be maintained and enforced by the identity provider 106.

An identity assertion in security assertion markup language (SAML), for example, contains a packet of security information that service providers 109 use to make access control decisions. SAML supports three types of statements: authentication statements, attribute statements, and authorization decision statements. Authentication statements assert to the service provider 109 that the client device 103 authenticated with the identity provider 106 at a particular time using a particular method of authentication. An attribute statement asserts that a client device 103 is associated with certain attributes. An authorization decision statement asserts that a client application 124 is permitted to perform a certain action relative to a resource offered by the service provider 109. Extensible access control markup language (XACML) and/or other languages can be employed.

The client applications 124 correspond to a variety of applications that are employed to access services provided by the service providers 109. The client applications 124 can include a web view component, whereby the client applications 124 interact with the service providers 109 to obtain network content by way of hypertext transfer protocol (HTTP) requests and responses. However, unlike a browser that is used to access various web-based applications, cookies set through one client application 124 cannot be accessed by another client application 124. The client applications 124 and the management application 121 can individually render a respective user interface 127 upon the display 118.

The client devices 103 a and 103 b can also include an authentication application 128, which is a special-purpose client application 124 used to complete multi-factor authentication, when multi-factor authentication is requested by the MFA adapter 116. The authentication application 128 can be executed on the same client device 103 a as the client application 124 that is being authenticated. Alternatively, the authentication application 128 can be executed on a different client device 103 b. In some cases, the functions of the authentication application 128 can be performed by the management application 121.

Turning now to FIG. 2, shown is a sequence diagram 200 illustrating one example of interaction between the client application 124, the authentication application 128, the service provider 109, and the identity provider 106. Functionality attributed to the client application 124, the authentication application 128, the service provider 109, and the identity provider 106 can be implemented in a single process or application or in multiple processes or applications. The separation or segmentation of functionality as discussed herein is presented for illustrative purposes only.

Beginning with step 203, the client application 124 sends an access request to the service provider 109. At step 206, the service provider 109 sends a redirection back to the client application 124 that causes client application 124 to redirect the access request to the identity provider 106. At step 209, the client application 124 sends an identity assertion request to the identity provider 106. At step 212, the identity provider 106 detects the type of client application 124 and the platform and responds by requesting authentication by way of an SSO credential 125 for the specific platform. This can correspond to a certificate challenge or a Kerberos challenge. At step 215, the client application 124 obtains the SSO credential 125, e.g., by requesting the SSO credential 125 from the management application 121 or from the operating system. The process of obtaining the SSO credential 125 can involve obtaining credentials from the user (e.g., a password or a numeric code) to verify that the user should have access to the SSO credential 125. Obtaining these credentials would thus correspond to the initial single sign-on for the user.

At step 218, the client application 124 uses the SSO credential 125 to authenticate with the identity provider 106. At step 221, the MFA adapter 116 of the identity provider 106 determines that multi-factor authentication is required. At step 224, the MFA adapter 116 of the identity provider 106 requests one or more supplementary authentication factors from the authentication application 128. The input device for providing multi-factor authentication can be different from the client device 103 executing the client application 124. For example, a user can access a social networking application on a smartphone using single sign-on. When multi-factor authentication is enabled, the user can provide a supplementary authentication factor using a laptop or tablet. At step 227, the authentication application 128 obtains the supplementary authentication factors from a user through a user interface 127 or one or more input devices (e.g., fingerprint scanners, retinal scanners). At step 228, the authentication application 128 sends the supplementary authentication factors to the MFA adapter 116 of the identity provider 106.

At step 230, the MFA adapter 116 of the identity provider 106 verifies the MFA credentials supplied by the authentication application 128. The identity provider 106 returns the identity assertion to the client application 124 at step 233. The identity assertion can include an authentication token generated by the identity provider 106. At step 236, the client application 124 provides the identity assertion to the service provider 109. At step 239, the service provider 109 verifies the identity assertion. The service provider 109 generates a session token, such as an OAuth token, and returns the session token at step 242.

A single sign-on can thereby be implemented for subsequent client applications 124 or for the client application 124 seeking to authenticate with another service provider 109. Thus, the process can repeat again for the client applications 124 a . . . 124N. Once the user is authenticated with the MFA adapter 116 for the purpose of authenticating client application 124 a, the user need not enter security credentials again for authenticating client application 124 b, unless perhaps due to inactivity or other events that could cause the identity of the user to be in question. That is to say, multi-factor authentication can be skipped based on a determination of the MFA adapter 116, and the validity of the SSO credential 125 can be relied upon. During the sign-on process, the user interface can remain stable to avoid “flipping” back and forth, making the process seamless to a user. In addition, multi-factor authentication can be required for some client applications 124 but not others, and different types of multi-factor authentication can be required for different client applications 124.

Moving on to FIG. 3, shown is a flowchart that provides one example of the operation of an identity provider 106. As an alternative, the flowchart of FIG. 3 can be viewed as depicting an example of elements of a method implemented in a computing device. Functionality attributed to the identity provider 106 can be implemented in a single process or application or in multiple processes or applications. The separation or segmentation of functionality as discussed herein is presented for illustrative purposes only.

Beginning with step 303, the identity provider 106 receives an authentication request such as an identity assertion request from a client application 124. The client application 124 has been redirected to the identity provider 106 by a service provider 109. The redirection can be performed, for example, by way of a hypertext transfer protocol (HTTP) redirection response. The identity provider 106 can determine a platform of the client device 103. The identity provider 106 can determine the platform by examining the user-agent string of the HTTP request. For example, the identity provider 106 can determine that the client device 103 corresponds to IOS, ANDROID, WINDOWS, BLACKBERRY, or other platforms based at least in part on corresponding identifiers contained in the user-agent string.

At step 306, the identity provider 106 requests authentication by the SSO credential 125. In some cases, this request can be based at least in part on the detected platform of the client device 103. Specifically, the identity provider 106 can request authentication using a platform-specific SSO credential 125 after querying a table of platforms based at least in part on information provided by the client device 103. Different types of security credentials and certificates can be used depending on the platform of the client device 103. For example, the SSO credential 125 can include a secure certificate, a Kerberos profile, or other credentials. Accordingly, to allow single sign-on from differing platforms, a platform adapter of the identity provider 106 can request the type of SSO credential 125 that is appropriate for the client device 103 that is requesting access. The SSO credential 125 can correspond to a management credential.

For example, when the platform is IOS, a platform adapter corresponding to an IOS-specific certificate adapter or Kerberos adapter can be used, such as an esso profile. When the platform is ANDROID, a platform adapter corresponding to a certificate adapter can be used. As additional examples, the OSX operating system can use a keychain, and WINDOWS 10 can use account provider credentials. The request for authentication can be performed by returning an HTTP response indicating that authorization is required. Further, the HTTP response can specifically request authentication by a particular protocol, such as the Kerberos protocol, through the use of a SSO credential 125.

At step 309, the identity provider 106 receives data associated with or generated by the SSO credential 125. In some cases, this data can be received in the initial authentication request. At step 312, the identity provider 106 performs a verification of the data associated with or generated by the SSO credential 125. The identity provider 106 can verify whether the SSO credential 125 is permitted to be used to authenticate specific client applications 124 or for specific service providers 109.

At step 315, the identity provider 106 determines whether the SSO credential 125 is verified. If the SSO credential 125 is not verified, the identity provider 106 denies the authentication at step 318 and an unauthorized message can be returned. Thereafter, the process proceeds to completion. If the SSO credential 125 is verified, the identity provider 106 continues to step 321.

At step 321, the identity provider 106 determines whether multi-factor authentication (MFA) is to be used. The MFA rules 117 can specify a variety of situations and factors in which MFA is to be used or is not to be used. For example, MFA can be required for authentication of specific client applications 124. MFA can be required for specific versions of a particular client application 124 or for specific operating system versions. In this regard, the MFA adapter 116 can determine the identity of the particular client application 124, the specific version of the client application 124, and/or the version of the operating system, which can be specified in the authentication request. Some client applications 124, particular versions of client applications 124, and/or particular operating system versions can be regarded as insecure or vulnerable to compromise, which can dictate a greater level of security and hence the use of MFA.

In another example, the MFA adapter 116 can determine the location of the client device 103 on which the client application 124 is executed. The location can be determined through reporting of global positioning system (GPS) coordinates, triangulation based on wireless access points and/or cell base stations, geolocation of an internet protocol address, or other approaches. A risk score can be computed based at least in part on the location and/or on other factors. For example, if the client device 103 has moved from one country to another, or has moved to a country associated with a heightened risk level, the risk score can be relatively high (e.g., exceeding a threshold), and at least on this basis, the MFA adapter 116 can determine that additional supplementary authentication factors are required. Other factors that can weigh towards a risk profile that would require MFA can include, a level of network traffic (e.g., high levels of network traffic can be associated with system compromises), a quantity of applications installed on the client device 103 (e.g., an increased number of applications can point to a device compromise), and others.

It is noted that whether MFA is required can change over time. Thus, for one authentication request from a client application 124 on a particular client device 103, MFA is not required, while for a subsequent authentication request from the same client application 124 on the particular client device 103, MFA can be required due to a change in a risk profile taking into account various factors (e.g., operating system version, application version, application identity, location, and so on).

If multi-factor authentication is not required, the identity provider 106 moves to step 324, where an identity assertion is generated and sent to the client application 124. The identity assertion can include security assertion markup language (SAML), extensible access control markup language (XACML), or other data. For example, the identity assertion can include an authentication token that is generated by the identity provider 106. Thereafter, the process proceeds to completion.

However, if multi-factor authentication is to be used, the MFA adapter 116 requests one or more supplementary authentication factors from an authentication application 128 at step 327. The MFA adapter 116 can request any of a variety of supplemental authentication factors, such as one-time passwords, smartcards, biometric identifiers, and so on. It is noted that the client application 124 does not natively support one or more of the supplemental authentication factors in various scenarios. The authentication application 128 can be executed on the same client device 103 or on a different client device 103 as compared to the client application 124. When executed on a different client device 103, any response from the authentication application 128 (e.g., a simple authentication approval) can be regarded as a proof of possession factor for the different client device 103. In some situations, the client device 103 on which the authentication application 128 is executed is an unmanaged client device, while the client device 103 on which the client application 124 is executed is a managed client device.

At step 330, the MFA adapter 116 receives the requested supplementary authentication factors from the authentication application 128. At step 333, the MFA adapter 116 performs a verification of the supplementary authentication factors. At step 336, the MFA adapter 116 determines whether the supplementary authentication factors are verified. If the supplementary authentication factors are not verified, the identity provider 106 denies the authentication at step 339 and an unauthorized message can be returned. Thereafter, the process proceeds to completion.

If the supplementary authentication factors are verified, the identity provider 106 continues to step 324. At step 324, an identity assertion is generated and sent to the client application 124. Thereafter, the process proceeds to completion.

Turning now to FIG. 4, shown is a flowchart that provides one example of the operation of an authentication application 128. Functionality attributed to the authentication application 128 can be implemented in a single process or application or in multiple processes or applications. The separation or segmentation of functionality as discussed herein is presented for illustrative purposes only.

Beginning with step 403, the authentication application 128 receives a multi-factor authentication (MFA) request from the MFA adapter 116 of the identity provider 106. The MFA request can specify a set of supplementary authentication factors that are to be requested of the user in order for a concurrent authentication of another client application 124 to proceed. The client application 124 that is requesting authentication can be executed in the same client device 103 as the authentication application 128 or in a different client device 103. The MFA request can specify that certain authentication factors are optional or required. In some cases, a certain number of authentication factors are required. As an example, a user can choose to provide a voice sample or a fingerprint scan, or to answer four of ten knowledge-based questions.

At step 406, the authentication application 128 renders a user interface 127 that requests the supplementary authentication factors of the user. For example, the authentication application 128 can request the user to provide a fingerprint scan, a retina scan, a voice sample, or other biometric identifiers. In other examples, the user can be requested to answer knowledge-based questions, enter a numerical code, use a smartcard, provide one-time passwords from a software or hardware token, or respond to other challenges. In still another example, the user can simply be asked to approve or deny the request, and upon approval, the authentication application 128 communicates the approval to the MFA adapter 116. In this regard, the authentication application 128 can prove its identity using stored registration credentials or using a token communicated to the authentication application 128 by way of a predefined communication channel, e.g., an email address, a telephone number, etc.

At step 409, the authentication application 128 receives the supplementary authentication factors. At step 412, the authentication application 128 sends the received supplementary authentication factors to the MFA adapter 116 of the identity provider 106. The MFA adapter 116 is subsequently able to verify the authentication factors and allow the concurrent authentication of the client application 124 to complete. Thereafter, the process proceeds to completion.

Continuing on to FIG. 5, shown is a flowchart that provides one example of the operation of a device management service 104. Functionality attributed to the device management service 104 can be implemented in a single process or application or in multiple processes or applications. The separation or segmentation of functionality as discussed herein is presented for illustrative purposes only.

Beginning with step 501, the device management service 104 receives an enrollment request from a client device 103. For example, a user can navigate to a certain uniform resource locator (URL) in a browser, the management application 121 can be installed on the client device 103, and a user can accept the terms of the enrollment. Then, a platform-specific management certificate can be sent to the management application 121. The platform-specific management certificate can be received within a profile which the client device 103 installs in a profile store as the management profile.

In step 503, the device management service 104 receives an authentication request from the management application 121 of the client device 103. The request can specify one or more security credentials, such as usernames, passwords, biometric identification, one-time passwords, and so on. At step 506, the device management service 104 determines that the security credentials that have been presented are valid. If the security credentials are not valid, an error can be generated.

At step 509, the device management service 104 sends one or more SSO credentials 125 to the client device 103. The SSO credentials 125 can be generated by a certificate authority corresponding to the device management service 104. In one use case, SSO credentials 125 can be employed to create a secure communications channel between the device management service 104 and the management application 121 for device management purposes. In another use case, the SSO credentials 125 can be used to facilitate authentication with an identity provider 106. Thereafter, the process proceeds to completion.

With reference to FIG. 6, shown is a flowchart that provides one example of the operation of a management application 121. Functionality attributed to the management application 121 can be implemented in a single process or application or in multiple processes or applications. The separation or segmentation of functionality as discussed herein is presented for illustrative purposes only.

Beginning with step 603, the management application 121 receives a single sign-on request from a client application 124. For example, the client application 124 can be prompted to use a SSO credential 125 in order to authenticate with an identity provider 106. At step 606, the management application 121 determines whether the user is already authenticated. If the user is not already authenticated, the management application 121 moves to step 609 and renders a user interface 127 on the display 118 that requests one or more security credentials from the user. At step 612, the management application 121 receives the security credentials through the user interface 127. The management application 121 continues to step 615. If the user is already authenticated by the management application 121, the management application 121 moves directly from step 606 to step 615.

At step 615, the management application 121 determines whether the client application 124 is authorized to receive the SSO credential 125. The management application 121 can make this determination with respect to the access rules 126 or by way of communication with the device management service 104. Examples of access rules 126 include detecting whether a device is jailbroken, uses a password of a given length or complexity, is used within a certain geographic area, has certain applications installed, has certain hardware devices (e.g., a fingerprint reader), and/or other meets other criteria relevant to the organization for whom the client device 103 is managed. If the client application 124 is not authorized, the management application 121 moves to step 618 and rejects the request. Thereafter, the process proceeds to completion.

If the client application 124 is authorized, the management application 121 moves to step 621 and determines whether the SSO credential 125 has been cached in the client device 103. If the SSO credential 125 has been cached, the management application 121 loads the SSO credential 125 from the cache at step 624. At step 625, the management application 121 provides the SSO credential 125 to the client application 124. Thereafter, the process proceeds to completion.

If the SSO credential 125 has not been cached, the management application 121 moves from step 621 to step 627 and authenticates with the device management service 104. To this end, the management application 121 can authenticate using the user-supplied credentials or a session or registration token. At step 630, the management application 121 sends a request for the SSO credential 125 to the device management service 104. At step 633, the management application 121 receives the SSO credential 125 from the device management service 104. At step 625, the management application 121 provides the SSO credential 125 to the client application 124. Thereafter, the process proceeds to completion.

Turning now to FIG. 7, shown is a flowchart that provides one example of the operation of a client application 124. Functionality attributed to the client application 124 can be implemented in a single process or application or in multiple processes or applications. The separation or segmentation of functionality as discussed herein is presented for illustrative purposes only.

Beginning with step 703, the client application 124 sends an access request to a service provider 109. At step 706, the client application 124 receives a redirection to the identity provider 106. The redirection can include a hypertext transfer protocol (HTTP) redirection response. At step 709, the client application 124 sends an authentication request to the identity provider 106. At step 712, the client application 124 receives a response requesting authentication by a SSO credential 125.

At step 715, the client application 124 obtains the SSO credential 125 from the management application 121. To this end, the client application 124 can send a request by a local uniform resource locator (URL) to the management application 121 and can also receive a response from the management application 121 by a local URL. The local URL used to invoke the management application 121 can include callback information such as a scheme name corresponding to the client application 124 so that the management application 121 can identify the client application 124 and return the requested SSO credential 125.

At step 718, the client application 124 sends data associated with or generated by the SSO credential 125 to the identity provider 106 as part of the authentication request. Subsequently, the MFA adapter 116 of the identity provider 106 can request additional supplementary authentication factors by way of an authentication application 128, but the client application 124 need not be aware of this process. At step 721, assuming that if multi-factor authentication was required, the MFA adapter 116 determines that the multi-factor authentication was successful, then the client application 124 receives an identity assertion from the identity provider 106. The identity assertion can include an authentication token generated by the identity provider 106. The identity assertion can correspond to a security assertion markup language (SAML) assertion or another assertion.

At step 724, the client application 124 authenticates with the service provider 109 using the identity assertion. At step 727, the client application 124 receives a session token from the service provider 109. For example, the session token can correspond to an OAuth token. Subsequently, at step 730, the client application 124 can authenticate with the service provider 109 to access resources. Thereafter, the process proceeds to completion.

Referring next to FIG. 8, shown is a flowchart that provides one example of the operation of a service provider 109. As an alternative, the flowchart of FIG. 8 can be viewed as depicting an example of elements of a method implemented in a computing device. Functionality attributed to the service provider 109 can be implemented in a single process or application or in multiple processes or applications. The separation or segmentation of functionality as discussed herein is presented for illustrative purposes only.

Beginning with step 803, the service provider 109 receives an access request from a client application 124. The service provider 109 then correlates this access request to the use of the identity provider 106 for authentication. At step 806, the service provider 109 sends a redirection response to the client application 124. This can include a hypertext transfer protocol (HTTP) redirection response. The redirection response can redirect the client application 124 to the identity provider 106. The redirection response can include security assertion markup language (SAML) that requests an identity assertion.

At step 809, the service provider 109 receives the identity assertion from the client application 124. At step 812, the service provider 109 verifies the identity assertion. For example, the identity assertion can include an authentication token generated by the identity provider 106, and the service provider 109 can confirm that the authentication token is authentic.

At step 815, the service provider 109 generates a session token. At step 818, the service provider 109 sets a session cookie including the session token with the client application 124. At step 821, the service provider 109 provides service access to the client application 124 based at least in part on the client application 124 presenting the session token, by way of a uniform resource locator (URL) or session cookie. Thereafter, the process can proceed to completion.

The flowcharts of FIGS. 3-8 and the sequence diagram of FIG. 2 show examples of the functionality and operation of implementations of components described herein. The components described herein can be embodied in hardware, software, or a combination of hardware and software. If embodied in software, each element can represent a module of code or a portion of code that includes program instructions to implement the specified logical function(s). The program instructions can be embodied in the form of, for example, source code that includes human-readable statements written in a programming language or machine code that includes machine instructions recognizable by a suitable execution system, such as a processor in a computer system or other system. If embodied in hardware, each element can represent a circuit or a number of interconnected circuits that implement the specified logical function(s).

Although the flowcharts and sequence diagram show a specific order of execution, it is understood that the order of execution can differ from that which is shown. For example, the order of execution of two or more elements can be switched relative to the order shown. Also, two or more elements shown in succession can be executed concurrently or with partial concurrence. Further, in some examples, one or more of the elements shown in the flowcharts can be skipped or omitted.

The client device 103, the device management service 104, the identity provider 106, the service providers 109, or other components described herein can include at least one processing circuit. Such a processing circuit can include, for example, one or more processors and one or more storage devices that are coupled to a local interface. The local interface can include, for example, a data bus with an accompanying address/control bus or any other suitable bus structure.

The one or more storage devices for a processing circuit can store data or components that are executable by the one or more processors of the processing circuit. For example, the identity provider 106, the device management service 104, the service providers 109, the management application 121, the client applications 124, the authentication application 128, and/or other components can be stored in one or more storage devices and be executable by one or more processors. Also, a data store, such as the identity data store 115 or the management data store 113 can be stored in the one or more storage devices.

The identity provider 106, the service providers 109, the management application 121, the client applications 124, the device management service 104, the authentication application 128, and/or other components described herein can be embodied in the form of hardware, as software components that are executable by hardware, or as a combination of software and hardware. If embodied as hardware, the components described herein can be implemented as a circuit or state machine that employs any suitable hardware technology. The hardware technology can include, for example, one or more microprocessors, discrete logic circuits having logic gates for implementing various logic functions upon an application of one or more data signals, application specific integrated circuits (ASICs) having appropriate logic gates, programmable logic devices (e.g., field-programmable gate array (FPGAs), and complex programmable logic devices (CPLDs)).

Also, one or more or more of the components described herein that include software or program instructions can be embodied in any non-transitory computer-readable medium for use by or in connection with an instruction execution system such as, a processor in a computer system or other system. The computer-readable medium can contain, store, and/or maintain the software or program instructions for use by or in connection with the instruction execution system.

A computer-readable medium can include a physical media, such as, magnetic, optical, semiconductor, and/or other suitable media. Examples of a suitable computer-readable media include, but are not limited to, solid-state drives, magnetic drives, or flash memory. Further, any logic or component described herein can be implemented and structured in a variety of ways. For example, one or more components described can be implemented as modules or components of a single application. Further, one or more components described herein can be executed in one computing device or by using multiple computing devices.

It is emphasized that the above-described examples of the present disclosure are merely examples of implementations to set forth for a clear understanding of the principles of the disclosure. Many variations and modifications can be made to the above-described examples without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure. 

1.-20. (canceled)
 21. A non-transitory computer-readable medium containing instructions that, when executed by the at least one computing device, cause the at least one computing device to perform stages comprising: receiving an authentication request from a managed client device, the authentication request including a first authentication factor corresponding to a single sign-on (“SSO”) credential, wherein the SSO credential is downloaded to the managed client device during or after enrollment with a device management service; determining, at an identity provider service separate from the managed client device, whether at least one second authentication factor should be requested; and in response to determining that the at least one second authentication factor should be requested: requesting the at least one second authentication factor from the managed client device; receiving the at least one second authentication factor from the managed client device; and authenticating the managed client device in response to verifying the first authentication factor and the at least one second authentication factor.
 22. The non-transitory computer-readable medium of claim 1, the stages further comprising: determining a location of the managed client device; and determining a risk score based at least in part on the location, wherein determining whether the at least one second authentication factor should be requested is based at least in part on the risk score.
 23. The non-transitory computer-readable medium of claim 1, the stages further comprising: determining a version of the managed client device; and determining that the at least one second authentication factor should be requested based on a version of an application executing on the managed client device.
 24. The non-transitory computer-readable medium of claim 1, the stages further comprising: determining a version of an operating system of the managed client device; and determining that the at least one second authentication factor should be requested when the version of the operating system corresponds to a particular operating system version.
 25. The non-transitory computer-readable medium of claim 1, wherein the stages further comprise determining that the at least one second authentication factor should be requested in response to verifying the first authentication factor.
 26. The non-transitory computer-readable medium of claim 1, wherein the first authentication factor corresponds to data generated by a secure certificate or a Kerberos profile.
 27. The non-transitory computer-readable medium of claim 1, wherein the authentication request originates at a first client application executing on the managed client device, wherein the at least one second authentication factor is not natively supported by the first client application, and wherein the at least one second authentication factor is requested from a second client application.
 28. A computing device that executes an identity provider service configured to cause the computing device to perform stages comprising: receiving an authentication request from a managed client device, the authentication request including a first authentication factor corresponding to a single sign-on (“SSO”) credential, wherein the SSO credential is downloaded to the managed client device during or after enrollment with a device management service; determining, at an identity provider service separate from the managed client device, whether at least one second authentication factor should be requested; and in response to determining that the at least one second authentication factor should be requested: requesting the at least one second authentication factor from the managed client device; receiving the at least one second authentication factor from the managed client device; and authenticating the managed client device in response to verifying the first authentication factor and the at least one second authentication factor.
 29. The computing device of claim 28, the stages further comprising: determining a location of the managed client device; and determining a risk score based at least in part on the location, wherein determining whether the at least one second authentication factor should be requested is based at least in part on the risk score.
 30. The computing device of claim 28, the stages further comprising: determining a version of an operating system of the managed client device; and determining that the at least one second authentication factor should be requested when the version of the operating system corresponds to a particular operating system version.
 31. The computing device of claim 281, wherein the stages further comprise determining that the at least one second authentication factor should be requested in response to verifying the first authentication factor.
 32. The computing device of claim 28, wherein the first authentication factor corresponds to data generated by a secure certificate or a Kerberos profile.
 33. The computing device of claim 28, wherein the authentication request originates at a first client application executing on the managed client device, wherein the at least one second authentication factor is not natively supported by the first client application, and wherein the at least one second authentication factor is requested from a second client application.
 34. A method, comprising: receiving an authentication request from a managed client device, the authentication request including a first authentication factor corresponding to a single sign-on (“SSO”) credential, wherein the SSO credential is downloaded to the managed client device during or after enrollment with a device management service; determining, at an identity provider service separate from the managed client device, whether at least one second authentication factor should be requested; and in response to determining that the at least one second authentication factor should be requested: requesting the at least one second authentication factor from the managed client device; receiving the at least one second authentication factor from the managed client device; and authenticating the managed client device in response to verifying the first authentication factor and the at least one second authentication factor.
 35. The method of claim 34, further comprising: determining a location of the managed client device; and determining a risk score based at least in part on the location, wherein determining whether the at least one second authentication factor should be requested is based at least in part on the risk score.
 36. The method of claim 34, further comprising: determining a version of the managed client device; and determining that the at least one second authentication factor should be requested based on a version of an application executing on the managed client device.
 37. The method of claim 34, further comprising: determining a version of an operating system of the managed client device; and determining that the at least one second authentication factor should be requested when the version of the operating system corresponds to a particular operating system version.
 38. The method of claim 34, further comprising determining that the at least one second authentication factor should be requested in response to verifying the first authentication factor.
 39. The method of claim 34, wherein the first authentication factor corresponds to data generated by a secure certificate or a Kerberos profile.
 40. The method of claim 341, wherein the authentication request originates at a first client application executing on the managed client device, wherein the at least one second authentication factor is not natively supported by the first client application, and wherein the at least one second authentication factor is requested from a second client application. 